Prerequisites

Before installing, choose one of the supported editor-and-agent setups.

System requirements

Supported host systems are Windows 10 or 11 (64-bit), macOS 15 or 26, Ubuntu 22.04, 24.04, or 26.04, and Fedora 43 or 44. Keep at least 500 MB of free disk space for the contexts. Development tools and generated projects need additional space.

Use PowerShell, bash, or zsh. On Windows, PowerShell 7.3 or later is recommended. PowerShell 5.1 in the VS Code integrated terminal can display ^U when Ctrl+U is pressed. See What should I do when PowerShell shows ^U? for a quick workaround.

Python 3.10 or later is required for the STM32Cube Embedded Software Context’s HAL/LL guidance. Python and the VS Code application are prerequisites: the toolkit never installs either one. The installer can resolve declared Python packages. VS Code extensions are installed only when explicitly requested. Other contexts can declare their own dependencies. Check the context pages or run cube agentic-ai doctor <project-folder> after deployment.

GitHub Copilot in VS Code requires the GitHub Copilot Chat extension ( GitHub.copilot-chat), and Claude Code in VS Code requires Anthropic’s Claude Code extension. Install the appropriate agent extension yourself. The toolkit installer does not install or manage either one. Its optional VS Code extension installation applies to extensions declared by toolkit contexts. Install the agent extension from the GitHub Copilot Chat extension Marketplace page or the Claude Code for VS Code guide.

For interpreter selection, package provisioning, and repair, see the Embedded Software Context.

The installer and contexts need network access to the Cube bundle registry. Remote contexts also need access to their documented services. See the relevant context page for service-specific network requirements.

VS Code build and debug

Build and DAP Debug contexts are available only for the VS Code target. Their extension, workspace, and debugger requirements are described in the Build and Debug context pages. The installer installs their declared extensions only when explicitly requested.

CMake without the Build Context

The Build Context is optional. Without it, an agent can guide a standard CMake workflow, but it does not replace a compatible compiler toolchain or project configuration. Follow the CMake preset and build instructions provided by the project or its toolchain.

Optional Cube bundles include cmake, ninja, and gnu-tools-for-stm32. Installing tools, editing build files, and starting the build require the user’s approval. The Build Context checks these prerequisites and obtains approval before it builds.